-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DO NOT MERGE] debug pypi workflow #241
Conversation
@webknjaz, current results from running the
anything else you want me to check? |
But what about the subdirs? |
Minimum allowed coverage is Generated by 🐒 cobertura-action against 99de9f8 |
this run runs
|
Ah, so /opt/conda/bin/python3: can't open file '/home/githubrunner/actions-runner/_work/_actions/pypa/gh-action-pypi-publish/release/v1/create-docker-action.py': [Errno 2] No such file or directory So it seems to me like GitHub Runner does put the host path into the The mount point is configured as |
So it seems to me like this is a case of a bug in GitHub Runner. And my hunch is that it's probably not caused by it being a hosted runner. It's likely caused by the use of the container setting on the job. @sroet to verify this, drop the container from the job and try again. If that's the case, I don't think we'll be attempting to support it (you can probably hack on your container and stick symlinks into it, but that's out of the scope). Though, I also noticed that you're not following the recommendation of keeping the build invocation out of the job that has elevated OIDC privileges. Perhaps, if you just split it according to https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/, the problem will disappear. |
That's not happening as dropping the container from a self-hosted runner will run the code on the actual host machine. Our host machines are not isolated/revertible enough to let random code run on it outside of a container.
I can try that, and if that doesn't work maybe push the publishing part to github-runners instead of self-hosted ones |
That's exactly what I meant. |
So, splitting out the job to run the upload on github runners instead of self-hosted ones seems to work (the failure is expected as this branch can't be valid for the trusted publishing setup we have on this project) |
I think all the necessary debugging has been done, so I will close this. |
No description provided.